We have found that the most useful events to log and study are those identified by the user and specified in his program. That way he can control the number of events to be logged and the grain size of the states that are represented.
In some cases, however, one wants to study the details of the internal operation of a p4 application, or get some idea of the behavior on one's program without going to the trouble of instrumenting it himself. To this end, p4 itself is instrumented with ALOG statements, although by default they are inactive. To get automatic logging of p4 events (including sending and receiving of each message) one needs first to link to a version of the p4 library that has been compiled with the line #define ALOG_TRACE uncommented out in the OPTIONS file, and secondly, to run with -p4log on the command line.
Machine-Specific Notes,Some Common Problems and their Solutions,Creating Logfiles for Upshot,Top